picogame: enable on pimoroni_picosystem - #11359
Conversation
The board has the 240x240 ST7789 over four-wire SPI that picogame's fast display path drives, plus the buttons and audio a game needs. It does not fit at -O3: the firmware is at 95.3% of the 1020 KB partition and the engine needs another 50 KB. At -O2 with the loop passes it keeps 140 KB free, within 1% of -O3 on this M0+.
|
This should be subsumed by the widened #11358, right? |
|
There are two things: So far, I've only enabled picogame on select RP2040 boards, but if you're okay with enabling it everywhere (which would make me happy 🙂), then we can do all of this in #11358 |
|
Did @tannewt suggest turning it on only for certain boards? Maybe I missed such a discussion. If so the below is not correct. Yes, I did mean that we could enable for all of RP2040, and for all of RP2350, except for the boards where it really doesn't fit, or doesn't make any sense. Some boards can't have an appropriate display due to lack of pins (though a precise audit on those is not so necesasry0, and some boards have a lot of frozen libraries due to choices by the manufacturer. So you could enable it on for all RP2xxx in |
Ya, I did. It is quite large to go everywhere. IMO I'd rather have it where we think folks will actually use it. |
OK, I'll withdraw what I said, but as to which boards are good, I think you have a better sense of that. But it might include plain Adafruit Feather RP2040 and Feather RP2350, because they can be used with the display Featherwings. |
3 participants
Enables picogame on pimoroni_picosystem: a 240x240 ST7789 over four-wire SPI, buttons and audio, which picogame's fast display path drives as it comes.
It does not fit at -O3: the firmware is at 95.3% of the 1020 KB partition and the engine needs another 50 KB. It builds at -O2 with five loop passes, which leaves 140 KB free and measures within 1% of -O3 on this M0+.